home *** CD-ROM | disk | FTP | other *** search
- Path: kryten.awinc.com!news
- From: bcarter@awinc.com (Bob Carter)
- Newsgroups: comp.sys.amiga.hardware
- Subject: Re: Help need with A3000 OS 3.1 Upgrade
- Date: 6 Jan 1996 19:02:39 GMT
- Organization: A & W Internet Inc.
- Message-ID: <3396.6579T709T970@awinc.com>
- References: <4cl4v4$7m4@ralph.vnet.net>
- NNTP-Posting-Host: pme610.onramp.awinc.com
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP)
-
-
-
- To Kevin Cox <kcox@hiwaay.net> and
- To Plasticman <plasman@katie.vnet.net> who wrote:
-
- > I guess I should say I am joining the club of people having problems
- > upgrading the A3000 to OS 3.1. Just got my official Villagetronics/Escom
- > copy of 3.1. BTW I am not a newbee at working inside my system.
-
- > Installed the ROM chips as per instructions, Chip 0 in socket U-181
- > (labeled ROM 1)and Chip 1 in socket U-180 (labled ROM 0). My motherboard
- > is a revision 8.9.
-
- This is fine, as on some A3000's the labeling on the motherboard is reversed.
- The surest way to socket your 3.1 roms properly is to take careful note of how
- your working 2.1 (or whatever) roms were in and position the new ones exactly
- the same way. The roms themselves may have their labels stuck on upside down.
- Make sure that the pin 1 marks (a small circular indent) are orientated to the
- front/center of the motherboard, as your old roms were.
-
- > Put everything back together and powered up. I get a flashing RED screen
- > and it sounds like the systems wants to keep restarting. All this
- > happens in the first seconds of power up and system goes nowhere. Rechecked
- > that ROM's are properly seated, no bent pins, etc.
-
- > Reinstalled my old softkicked ROMS and everything works fine. Any and
- > all ideas gratefully accepted.
-
- The first thing to check are the settings of the nonvolatile memory of the
- A3000's clock chip. You do this by running a utility such as setbatt. BTW, I
- had the same problems as you guys and this was the bad nasty that kept my roms
- from booting up properly - the recurrent rebooting, no hard/floppy drive
- boot access, et al. Anyway, here are the default settings on my system
- (A3000/25 rev8.9) as reported by setbatt, and what you should have too:
-
- The SCSI selection timeout is SHORT (128 milliseconds).
- Logical SCSI units above 0 ARE NOT accessed.
-
- The SCSI controller's host ID is 7.
- Synchronous transfer is NOT INITIATED.
- Fast synchronous transfer is NOT INITIATED (<=5MB/s).
- SCSI-2 tagged queuing is DISABLED.
-
- The only parameter you may have to set differently is the SCSI timeout, which
- should be set to LONG if you have a slow-to-spinup-to-speed harddrive.
-
- Once this is done reinstall your OS3.1 roms and power up!
-
- Still having problems? Try accessing the bootscreen by holding down both mouse
- buttons when you power up or reboot. If you can't access this screen then I
- dare say I don't know what other advice to offer, other than recheck the roms'
- orientation and look for bent pins. Sorry... :-(
-
- One last caveat...
-
- If you've gotten this far and the OS is accessing your harddrive but it's
- still crashing, which is what happened to me, then you're having a problem
- with your startup sequence. On my A3000 the SetPatch command does not work as
- advertised. I changed the command in my startup-sequence from:
-
- C:SetPatch QUIET
-
- to:
-
- C:SetPatch NOCACHE NOAGA QUIET
- C:CPU >NIL: CACHE
-
- and all was well. I don't know why exactly, but the A3000 doesn't like the
- Setpatch line as it comes in the stock startup-sequence script. The second line
- I added turns on the CPU caches. It isn't really necessary, but I did it anyway,
- on someone's suggestion.
-
- Good luck,
-
- Bob (exmember of the club)
-
- ____________________
- | |
- | Bob Carter |
- | bcarter@awinc.com |
- |____________________|
-
-
- On a clear disk, you can seek forever.
-
-